Using Architectural Decisions
نویسندگان
چکیده
There are increasing demands for the explicit representation and subsequent sharing and usage of architectural decisions in the software architecting process. However, there is little known on how to use these architectural decisions, or what type of stakeholders need to use them. This paper presents a use case model that arose from industrial needs, and is meant to explore how these needs can be satisfied through the effective usage of architectural decisions by the relevant stakeholders. The use cases are currently being validated in practice through industrial case studies. As a result of this validation, we argue that the usage of architectural decisions by the corresponding stakeholders can enhance the quality of software architecture.
منابع مشابه
Eliciting Architectural Decisions from Requirements using a Rule-based Framework
Making architectural decisions based on requirements, analyzing cost-benefit trade-offs, and keeping design options open is a difficult task. Existing work on classification of architectural styles and features of reusable components, and derivation of relevant architectural styles provides useful heuristics to the task, but it remains to be largely a laborintensive activity. In this paper, we ...
متن کاملPreserving the Quality of Architectural Tactics in Source Code
Preserving the Quality of Architectural Tactics in Source Code by Mehdi Mirakhorli In any complex software system, strong interdependencies exist between requirements and software architecture. Requirements drive architectural choices while also being constrained by the existing architecture and by what is economically feasible. This makes it advisable to concurrently specify the requirements, ...
متن کاملHarmonizing architectural decisions with component view models using reusable architectural knowledge transformations and constraints
Architectural design decisions (ADDs) have been used in recent years for capturing design rationale and documenting architectural knowledge (AK). However, various architectural design views still provide the most common means for describing and communicating architectural design. The evolution of software systems requires that both ADDs and architectural design views are documented and maintain...
متن کاملEvolution-Centered Architectural Design Decisions Management
Software architecture is considered as a set of architectural design decisions. Managing the evolution of architectural design decisions helps to maintain consistency between requirements and the deployed system, and is also necessary for reducing architectural knowledge evaporation. In this paper, we propose a UML metamodel based on the Triple View Model from our previous research work. The UM...
متن کاملReducing Architectural Knowledge Vaporization by Applying the Repertory Grid Technique
The architecture of a software-intensive system is the composition of architectural design decisions. These decisions are an important part of Architectural Knowledge (AK). Failure to document architectural design decisions can lead to AK vaporization and higher maintenance costs. To reduce AK vaporization, we propose to apply the Repertory Grid Technique (RGT) to make tacit knowledge about arc...
متن کاملذخیره در منابع من
با ذخیره ی این منبع در منابع من، دسترسی به آن را برای استفاده های بعدی آسان تر کنید
عنوان ژورنال:
دوره شماره
صفحات -
تاریخ انتشار 2006